Mastercard Developers

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Free hosted MCP server that gives AI agents Mastercard Developers docs, integration guides and API specs.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Mastercard Developers": {
      "url": "https://developer.mcp.mastercard.com/",
      "transport": "streamable-http"
    }
  }
}

Measured tools (9)

• get-services-list read-only

  Lists all available Mastercard Developers Products and Services with their basic information including title, description, and service id. IMPORTANT: The response contains both 'Products' (business offerings) and 'Services' (technical APIs with serviceIds). Use "serviceId" for each service for any tools that require serviceId as the parameter.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get-documentation read-only

  Provides an overview of all available documentation for a specific Mastercard service including section titles, descriptions, and navigation links. It takes one argument: - serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')

  Parameters:

  • serviceId (required) — string — The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get-documentation-section-content read-only

  Retrieves the complete content for a specific documentation section. IMPORTANT: A section is not a single page, but rather a collection of pages that are grouped together. It takes two arguments: - serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations') - sectionId (str): The specific section identifier within the service documentation (e.g., 'getting-started', 'api-reference')

  Parameters:

  • serviceId (required) — string — The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')
  • sectionId (required) — string — The specific section identifier within the service documentation (e.g., 'getting-started', 'api-reference')

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get-documentation-page read-only

  Retrieves the complete content of a specific documentation page. Takes one argument: - pagePath (str): The full path to the documentation page (e.g., '/send/documentation/use-cases/index.md')

  Parameters:

  • pagePath (required) — string — The full path to the documentation page (e.g., '/send/documentation/use-cases/index.md')

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get-oauth10a-integration-guide read-only

  Retrieves the comprehensive OAuth 1.0a integration guide including step-by-step instructions, code examples, and best practices for Mastercard APIs. Optionally specify a programming language to get language-specific examples and guidance.

  Parameters:

  • language — string — Programming language for language-specific examples and guidance

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get-oauth20-integration-guide read-only

  Retrieves the comprehensive OAuth 2.0 integration guide including step-by-step instructions, code examples, and best practices for Mastercard APIs. Optionally specify a programming language to get language-specific examples and guidance.

  Parameters:

  • language — string — Programming language for language-specific examples and guidance

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get-openfinance-integration-guide read-only

  Retrieves the comprehensive Open Finance (previously known as Open Banking) integration guide including setup instructions, API usage examples, and implementation best practices.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get-api-operation-list read-only

  Provides a summary of all API operations for a specific Mastercard API specification including HTTP methods, request paths, titles, and descriptions. It takes one argument: - apiSpecificationPath (str): The path to the API specification file e.g., '/open-finance-us/swagger/openbanking-us.yaml')

  Parameters:

  • apiSpecificationPath (required) — string — The path to the API specification file (e.g., /open-finance-us/swagger/openbanking-us.yaml)

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get-api-operation-details read-only

  Provides detailed information about a specific API operation including parameter definitions, request and response schemas, and technical specifications for successful API calls. It takes three arguments: - apiSpecificationPath (str): The path to the API specification file (e.g. The path would be /open-finance-us/swagger/openbanking-us.yaml for https://static.developer.mastercard.com/content/open-finance-us/swagger/openbanking-us.yaml, https://developer.mastercard.com/open-finance-us/swagger/openbanking-us.yaml, or /open-finance-us/swagger/openbanking-us.yaml) - method (str): The HTTP method of the operation (e.g., GET, POST, PUT, DELETE) - path (str): The API endpoint path from the specification (e.g., /payments, /accounts/{id})

  Parameters:

  • apiSpecificationPath (required) — string — The path to the API specification (e.g., /open-finance-us/swagger/openbanking-us.yaml)
  • method (required) — string — The HTTP method of the operation (e.g., GET, POST, PUT, DELETE)
  • path (required) — string — The API endpoint path from the specification (e.g., /payments, /accounts/{id})

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.